SPEC-PWF-SCH · v0.1 29 June 2026 Owner: Platform team
Drill-down of the master workflow map (SPEC-PWF). This process is a view over the spec — its requirements live in the PRD set (Portal PTL-11, Admin ADM-7, Partners PAR-15), its events & services in the domain set (Field owns scheduling, SVC-20), its entities in the ERD (VisitProposal · VisitProposalOption · SchedulingPreference, DM-57…59). Lanes, steps and events render from workflow/workflow-catalog.js — nothing is defined twice. See §4 for the per-step links.
1Trigger, outcome & lanes
What starts this process, where it ends, who acts and on which surfaces. Scheduling spans three apps: RiverSync proposes (Admin), the customer chooses (Portal), the servicing partner works the visits it services within scope (Partners).
RiverSync Co., Ltd. · BangkokSPEC-PWF-SCH · 1 of 4
2The flow
Top to bottom in sequence; lanes are the actors. Node shape follows the master conventions — pills start and end the process, grey nodes are backbone events, diamonds are decisions. The decline branch loops back to a fresh proposal.
Service scheduling — propose → select. Each step traces to a requirement in the table overleaf.SPEC-PWF-SCH · flow
RiverSync Co., Ltd. · BangkokSPEC-PWF-SCH · 2 of 4
3Steps
Each row is one node on the swimlane: who acts, what happens, the domain event it emits, and the requirement or rule it traces to.
RiverSync Co., Ltd. · BangkokSPEC-PWF-SCH · 3 of 4
4Related documentation
Every id, event, service and entity this process touches — each linked to the document that owns it. This is how you hop from a step back to the requirement, the service or the data model behind it.
5Rules in play
The WF-rules that bind this workflow — the master holds the full set; the DM-rules (ERD) and SVC-rules (Domain) they extend stay with those documents. Note WF-7: the partner read defers to the single partner-scope resolver (SVC-6), and WF-5: RiverSync proposing into a customer tenant is audited into both trails.
6Revision history
Version
Date
Changes
0.1
29 Jun 2026
First draft — service scheduling joins the operations group as the propose → select negotiation across Portal · Admin · Partners. New requirements PTL-11 · ADM-7 · PAR-15; new entities VisitProposal · VisitProposalOption · SchedulingPreference (DM-57…59); Field owns scheduling (SVC-20); events visit.proposed · visit.proposal-accepted · visit.proposal-declined.
RiverSync Co., Ltd. · BangkokSPEC-PWF-SCH · 4 of 4
